Viewing and purging the HSM event log
ProtectServer 3 HSMs maintain event logs in order to provide a means of tracking serious hardware or consistent operational faults. It is the device administrator’s task to view and purge HSM event log data.
When the HSM event log is full, the HSM will no longer store new event records and will need to be purged.
Note
The HSM event log cannot be purged until it is full.
To view the HSM event log
-
Launch the administration utility from the Start menu by selecting Start > Programs > SafeNet > ProtectToolkit M > gmadmin.
-
Select the desired HSM from the Active Adapters list.
-
Open the Adapter menu and select View Event Log.
-
The administration utility will now prompt for the device administrator password. Correct entry of the password will result in the event log being displayed.
-
The event log is shown as a series of pages. If there are more than one page of event log entries, the operator can navigate through the pages via the first, prev, next, last buttons.
To purge the event log
-
Launch the administration utility from the Start menu by selecting Start > Programs > SafeNet > ProtectToolkit M > gmadmin.
-
Select the desired HSM from the Active Adapters list.
-
Open the Adapter menu and choose Purge Event Log.
-
The administration utility will now prompt for the device administrator password. Correct entry of the password will result in the event log being purged.
Note
The event log can also be purged via the View Event Log dialog by clicking the Purge button.
The following table lists the error entries that may be generated by the ProtectServer 3 HSM firmware and written to the HSM’s event log.
Event records are written sequentially and chronologically. If the date and time of a later entry in the log is stating an earlier time than an entry preceding it, it indicates that the real-time clock or audit information has been altered.
Error code | Description |
---|---|
CPROV_BL_UPGRADED | Boot loader upgrade performed. Parameter 1: Mod Parameter 2: Version |
CPROV_OS_UPGRADE_FAILED | OS upgrade failed. |
CPROV_OS_UPGRADED | OS upgrade performed. Parameter 1: Mod Parameter 2: Version |
ERR_HOT_TAMPER | Hot tamper detected. |
ERR_HSM_HALT_ON_EXT_TAMPER | HSM was previously halted on external tamper. |
ERR_HSM_HALT_ON_GENERAL_ERROR | HSM was previously halted on unrecoverable general error. |
ERR_HSM_HALT_ON_INT_TAMPER | HSM was previously halted on internal tamper. |
ERR_HSM_HALT_ON_LO_BAT | HSM was previously halted on low battery. |
ERR_HSM_HALT_ON_OVER_TEMP | HSM was previously halted on over temperature. |
ERR_HSM_HALT_ON_OVER_VOLTAGE | HSM was previously halted on over voltage. |
ERR_HSM_HALT_ON_UNDER_TEMP | HSM was previously halted on under temperature. |
ERR_HSM_HALT_ON_UNDER_VOLTAGE | HSM was previously halted on under voltage. |
ERR_RTC_BATTERY_LOW | RTC: battery low. |
FM_MODULE_FAIL | FM Module failed to load. Parameter 1: Mod Parameter 2: Version |
FM_OP_DISABLE | FM disabled. Parameter 1: Mod Parameter 2: Version |
FM_OP_DOWNLOAD | FM download performed. Parameter 1: Mod Parameter 2: Version |
KEYGEN_ERR_PAIRWISE | Key generation: pairwise consistency check failed. |
LOG_DANGLING_DIR_FOUND | Flash SMFS has detected a dangling DIR entry. |
LOG_EVENT_LOG_PURGED | Event log has been purged. |
LOG_FACTORY_RESET | Factory reset performed on HSM. |
LOG_INIT_SRAM_COMMAND | Soft tamper command executed. |
LOG_INITIALIZING_SRAM | Initializing the SRAM after a tamper. |
POST_ERR_CODE | Code checksum check failed. |
POST_ERR_FDS | Flash data storage error. |
POST_ERR_FW | FW integrity check failed. |
POST_ERR_KAT | Known answer test failed. |
POST_ERR_RNG | RNG self test failed. |
POST_ERR_SMFS | SMFS error. |
PROT_CIPHER_DUPLICATE | Protection: duplicate initial value provided for SMS cipher. |
PROT_NO_SMPR | Protection: adapter SMPR not found. |
PTKC_CFG_CHNG | ProtectToolkit-C configuration change. Parameter 1: New value Parameter 2: Old value |
SMFS_ERR_ERROR | Unable to read/write/access SMFS. |
SMFS_ERR_NOT_INITED | Flash storage uninitialized. |